feat(history): auto-expand commits on file navigation boundary #212
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why?
When browsing repository history with
:CodeDiff history, reaching the last file in a commit and pressing]fwraps back to the first file of the same commit. This creates friction when reviewing changes across multiple commits.What?
Auto-expand commits when navigating across commit boundaries:
]f): At last file → expands next commit, selects its first file[f): At first file → expands previous commit, selects its last fileImplementation uses shared helpers:
collect_commit_files: Recursively collects files (handles tree mode with nested directories)find_current_position: Locates commit/file indices for boundary detectionupdate_cursor: Updates history panel cursor positionNotes
load_commit_fileswith callback pattern for responsive UIlistandtreeview modeskeymaps.view.next_file/prev_file)Recording
trimmed.mov